Looks good, just one quick note :)

@btd1337

Please, consider to use 2 branchs: master (stable code), develop (development code).

I think that you could refer to GitHub releases for stable versions instead. Also, thanks for your hackup-git AUR package :)

@pikpok Thanks for the feedback. Unfortunately I manage many packages in AUR, I could not keep everyone up to date if it depended on the releases because every time a new version is released pkgbuild must be updated manually.

@btd1337 I'm not experienced in PKGBUILDS but perhaps https://developer.github.com/v3/repos/releases/#get-the-latest-release could be useful?

@mdh34 I don't know convert this to PKGBuild. Look how other users implement stable packages:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=yay

and now, how Is implemented in latest commit:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=hackup-git

@btd1337 I meant that stable packages shouldn't be fetched from git branch but rather from tarballs of tags representing specific versions (which releases come from), just as in yay package you mentioned. This way you need only to update version field in PKGBUILD when a new release happens, and user can also easily switch to previous version of the package before makepkg. And if you want to have users of your package notified of update (via AUR managers for example), you need to update the PKGBUILD anyway.

@pikpok Like I said I manage many packages. I will not be able to update every time there is a new version. If this is an app you enjoy, consider managing it. It will be a great learning experience.